Search results for "SOFTWARE DEVELOPMENT PROCESS"
showing 10 items of 33 documents
How to Comprehend Large and Complicated Systems
2002
The basic problem at early analysis stage of the development life cycle is how to quickly comprehend a large and complicated system. One of the ways to comprehend such a system is to build an object model, as it was suggested by the pioneers of object modelling approach such as J.Rumbaugh1 and J.Martin2. In up-to-date terminology it means building a UML class diagram. The authors have got convinced in their everyday practice on extreme efficiency of this type of modelling, though at the same time a significant experience for this job is also required. To make this job easier, a modelling methodology must be developed. The goal of this paper is, on the one hand, to give some methodological r…
Improving the Reuse Process is Based on Understanding the Business and the Products: Four Case Studies
2002
The reuse of software engineering assets has been proposed as the most promising alternative for improving productivity and software quality. The improvement of reuse requires understanding of suitable reuse strategies and the software process. In four industrial cases the reuse process is analyzed for the purpose of its improvement and remarkable differences between successful processes are found. Those differences are due to differences in the products and businesses of the analyzed companies. In some cases the product line approach fits the business very well and high level of reuse can be achieved by using it. In other cases the black-box approach to reuse has turned out to suit the bus…
Introduction
2014
Nowadays, software engineers face a wide range of particular application domains such as electronic commerce, enterprise resource planning, mobile computing, self-organisation, pervasive and adaptive computing, etc. The resulting heterogeneity and required functionalities call for complex systems and open architectures that may evolve dynamically over time so as to accommodate new components and meet new requirements. This is probably one of the main reasons why the agent metaphor and agent-based computing are gaining momentum in these areas.
Explaining Change Paths of Systems and Software Development Practices
2010
This chapter discusses how systems development practices are shaped. Based on interviews conducted in ten development organizations and previous literature, we identify eight types of change paths in systems development practices: emergence, adoption, idealization, formalization, abandonment, informalization, entropy, and disobedience. We argue that the eight change path types provide an integrated theoretical framework on the study of how systems development practices change in organizations, projects, and among individual developers in a given context. We discuss how this framework complements existing theories and concepts of the contemporary literature on systems development.
MetaEdit+ A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment
1996
Computer Aided Software Engineering (CASE) environments have spread at a lower pace than expected. One reason for this is the immaturity of existing environments in supporting development in-the-large and by-many and their inability to address the varying needs of the software developers. In this paper we report on the development of a next generation CASE environment called MetaEdit+. The environment seeks to overcome all the above deficiencies, but in particular pays attention to catering for the varying needs of the software developers. MetaEdit+ is a multi-method, multi-tool platform for both CASE and Computer Aided Method Engineering (CAME). As a CASE tool it establishes a versatile an…
A Proposal for Modelling Usability in a Holistic MDD Method
2014
Holistic methods for Model-Driven Development (MDD) aim to model all the system features in a conceptual model. This conceptual model is the input for a model compiler that can generate software systems by means of automatic transformations. However, in general, MDD methods focus on modelling the structure and functionality of systems, relegating the interaction and usability features to manual implementations at the last steps of the software development process. Some usability features are strongly related to the functionality of the system and their inclusion is not so easy. In order to facilitate the inclusion of functional usability features from the first steps of the development proc…
The Place and Role of Security Patterns in Software Development Process
2006
Security is one of the key quality attributes for many contemporary software products. Designing, developing, and maintaining such software necessitates the use of a secure-software development process which specifies how achieving this quality goal can be supported throughout the development life-cycle. In addition to satisfying the explicitly-stated functional security requirements, such process is aimed at minimising the number of vulnerabilities in the design and the implementation of the software. The secure software development is a challenging task spanning various stages of the development process. This inherent difficulty may be to some extent alleviated by the use of the so-called…
Composition of a New Process to Meet Agile Needs Using Method Engineering
2005
The need of developing a new software engineering process to allow the quick prototyping of some robotic applications and meet the requests by some companies for a development process that was shorter than PASSI, gave us the opportunity of applying our studies on the assembling of a new SEP by reusing parts (called method fragments) from other processes. In this paper we discuss our approach that, starting from the method engineering paradigm, adapts and extends it considering specific agent-oriented issues like the multi-agent system meta-model. The final result of our experiment (Agile PASSI) is presented together with the requirements that motivated its structure. © Springer-Verlag Berli…
Understanding and managing process interaction in IS development projects
2012
Published version of an article from the book: Nordic Contributions in IS Research. Also available on SpringerLink:http://dx.doi.org/10.1007/978-3-642-32270-9_2 Software-based information systems must be developed and implemented as a part of business change. This is a major challenge, since business change and the development of software-based information systems usually are performed in separate processes. Thus, there is a need to understand and manage the relationship between these two kinds of processes. In this paper we draw on a longitudinal case study. We suggest a framework to analyze the case as interaction between software development processes and organizational change processes.…
Apathy Towards the Integration of Usability Work: A Case of System Justification
2016
In this article we report from a case study of a software development organization and we study in particular the developers’ and product managers’ attitudes towards integrating usability work into software development. We offer explanations based on system justification theory illuminating what would-be integrators might be up against. The analysis shows how the developers only pay lip service to usability work and how they treat users superficially. It further shows how that leads to stereotyping of usability designers and users in order to preserve status quo, and how internalization of inequality between the developers and usability designers rationalizes the preservation of status quo.…